home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
programs
/
purity25.zip
/
PURITY.DOC
< prev
next >
Wrap
Text File
|
1993-05-01
|
11KB
|
274 lines
PURITY 500
v2.5
May 1, 1993
PCBoard 14.x and GAP 4.x
WILDCAT!, Spitfire
QBBS, RBBS, RA
WWIV,TriBBS
by
Dennis Maidon
PAROLE TECHNOLOGIES
311 Buffalo Rd
Clayton, NC 27520
(919) 965-3600 -> Voice
(919) 965-9885 -> FAX
The Parole Board BBS
(919) 965-4696 -> US Robotics Dual Standard
OVERVIEW
________
This ZIP file was created using the -AV function of PKZIP. If
my AV is missing then this file may not be complete of has been
tampered with. Complete and current editions of this program
are always available for D/L on The Parole Board BBS. If the AV
is missing please complain to your sysop to stop the practice of
removing AV's as this is your assurance from the programmer that
the file is complete and virus free.
INSTALLATION
____________
Installation is fairly easy and straight-forward. The following steps and
examples should have you up and running in a very short period of time.
It is assumed that you are familiar with setting up DOORS on your system.
To this end, only examples of the configuration file and Door batch file
are described.
1) Create a directory to hold all PURITY 500 files
2) Unzip PURITYxx.ZIP into the the above directory
3) Run 'INSTALL.BAT' This will unzip all the files and create the
necessary subdirs.
4) Create a configuration file, with a name of your choice, or
modify the PURITY.CFG file that is enclosed.
A description follows:
C:\WILDCAT\CALLINFO.BBS ──┐ <- For Wildcat! 2.x
C:\WC30\USERINFO.DAT │ <- For Wildcat! 3.0 (Must point to NODEx dir)
C:\PCB\PCBOARD.SYS │ <- For PCBoard using PCBOARD.SYS only
C:\PCB\USERS │ <- For PCBoard using USERS only
C:\BBS\GTUSER.BBS │ <- For GT Power systems
C:\BBS\DOOR.SYS │ <- For Systems that support DOOR.SYS
C:\BBS\DORINFOx.DEF │ <- For QBBS/RBB/RA. Replace x with Node #.
C:\BBS\SFDOORS.DAT │ <- For Spitfire
C:\BBS\TRIBBS.SYS │ <- For TriBBS
C:\BBS\CHAIN.TXT ───┘ <- For WWIV
The Parole Board BBS <- Your BBS Name
Dennis <- SysOp's First Name
Maidon <- SysOp's Last Name
00000 <- Registration Number
YES <- Create Log
C:\WC\BULL\BULL1.SCR <- Path and Name of Color Bulletin
C:\WC\BULL\BULL1.BBS <- Path and Name of ASCii Bulletin
15 <- Minimum questions before scoring
100 <- Minimum security level allowed in door.
WC <- "WC" = WC!3.x "PCB" = PCBoard "N" = ANSI/ASCii
RIP <- "RIP" create RIP bulls "N" do not create
Edit this .CFG file to suit your individual BBS. All 12 lines MUST
be present.
Line 1: This line points to where PURITY.EXE will find the callers
information file. Just include the line that your particular
BBS uses. DO NOT put all of them in the CFG file.
Line 2: Place the name of your BBS on this line.
Line 3: SysOp's first name goes here.
Line 4: SysOp's last name goes here.
Line 5: Your Registration Number goes here if registered
Line 6: YES to create .LOG log or leave blank
Line 7: Enter the complete path and name of the ANSI bulletin that
you want PURITY 500 to create.
Line 8: Enter the complete path and name of the ASCii bulletin that
you want PURITY 500 to create. If You specify "WC" or
"PCB" on line #11, you may leave this line blank.
Line 9: Minimum # of questions to answer before user is scored
Line 10: The minimum security level that is allowed in the door.
Line 11: Type of bulletins you wish to create. "WC" = Wildcat!3.x
color codes. "PCB" = PCBoard color codes "N" = ANSI/ASCii
bulletins
Line 12: If you wish to create a RIP style bulletin, place "RIP" on
this line. Place "N" if you do not want RIP bulletins.
NOTE: There are 2 additional lines necessary when using GTUSER.BBS. Since
this file does not provide the ComPort% and NodeNum% variables, advise
your Door users to add them to this .CFG file on lines 5 and 6
respectively. Both variables will default to 1.
If you use the above CFG file be sure to remove all remarks and use
a pure ASCII editor such as EDLIN or QEDIT. Hidden control codes could
cause the program to depart for worlds unknown.
4) Create a batch file or modify the PURITY file supplied. A
description of this file follows:
ECHO OFF
CD \DOORS\PURITY Location of PURITY 500 files
PURITY PURITY.CFG EXE filename and CFG filename
CD\WCAT
CAT.BAT
5) When running in more than one node, be sure to supply a
different configuration name for each node (your choice of name).
EX: PURITY1.CFG PURITY2.CFG
PURITY 500 has been tested under LIVECAT! and performs very well.
NOTE: DoorFrame supports COM 1-4 on the standard IRQ's - COM1/COM3 = IRQ4 and
COM2/COM4 = IRQ3. If you wish to use a non-standard IRQ, add the IRQ
number after the configuration filename. Let's assume your Door is
called FOOBAR and you want to use COM1 and IRQ5. The command line
passed to your Door would be:
FOOBAR FOOBAR.CFG /5
FOOBAR FOOBAR.CFG *5
The /5 tells DoorFrame to use IRQ5 rather than the standard IRQ4 that
is normally used with COM1. No /x parameter is needed for the standard
IRQ's.
Fossil Driver Support
---------------------
DoorFrame supports the use of Fossil drivers. To tell your Door to use the
Fossil driver instead of the standard COM ports, just put /FD on the command
line when running the door. For example:
MYDOOR MYDOOR.CFG /FD
MYDOOR MYDOOR.CFG *FD
indicates that a Fossil driver is present and should be used. If no Fossil
driver is detected, DoorFrame will print a message to that effect and exit
the door gracefully.
NOTE: You may now use one (1) CFG file for multi-node by using the
environment variables.
When specifying the location of the system file on line 1 of the doors .CFG
file, you may use the environment variables %pcbdrive%, %pcbdir%, %pcbnode%,
and %wcnodeid%. Some examples:
PCBoard:
USERS.SYS in C:\PCB - %pcbdrive%%pcbdir%\USERS.SYS
USERS.SYS in C:\PCB\NODE1 - %pcbdrive%%pcbdir%\NODE%pcbnode%\USERS.SYS
Wildcat!:
USERINFO.DAT in C:\WC30\WCWORK\NODE1 - C:\WC30\WCWORK\NODE%WCNODEID%
Non-PCBoard systems may use the PCB environment variables by setting them
in either AUTOEXEC.BAT or in the batch that runs the door. For example:
SET PCBDRIVE=C:
SET PCBDIR=\BBSDIR
SET PCBNODE=1
--------------
Create the CFG file(s) for you particular BBS. You will also need a DOORx.BAT
to run the door. This one is simple.
@ECHO OFF
CD \DOOR\PURITY
PURITY PURE.CFG /5
──┬─
┌──────────────┘
└ If you are running non-Standard Com ports on your BBS, you will need to pass
the proper IRQ to the door. It doesn't hurt to pass the IRQ even if they are
standard. If a user enters the door and it just sits there acting sort of
stupid, it's probably looking for the correct IRQ. Always pass it on the
command line and there will be no question. Some networks have a problem
using the "/" symbol. P500 will now accept an asterisk "*" in place of
the "/". You may also use the environment variable in the DOORx.BAT file to
pass info to the door.
PURITY PURE%WCNODEID%.CFG /%WCIRQID%
Make sure you DO have the variables set if you use this method.
-----------------
Be sure to read all the READ.ME, README.1ST AND UPGRADE.DOC files
if they are included in the package. They sometimes contain some very
useful information. <G> Of course you can do like me, just set the darn
thing up without the docs then fuss at the door author for not making it
simple enough to work the first time.
When a user first log onto ' PURITY 500' the program checks his
security level to make sure that he has a high enough level to enter the
door. it will then check the <user>.USR files to see if he has been
locked out of the door by the sysop. If the user passes both of these
tests then he may proceed in playing P500. This info will be used each
time the user logs on to pick up his ALIAS and other info.
LEGALITIES
__________
THIS SOFTWARE AND ACCOMPANYING MATERIALS ARE DISTRIBUTED "AS IS"
WITHOUT WARRANTY, EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT
LIMITED TO ANY IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL ANYONE INVOLVED WITH
THE CREATION AND PRODUCTION OF THIS PRODUCT BE LIABLE FOR INDIRECT,
SPECIAL, OR CONSEQUENTIAL DAMAGES, ARISING OUT OF ANY USE THEREOF
OR BREACH OF ANY WARRANTY.
DISTRIBUTION
____________
You may make this file available for downloading from your BBS or you may
upload it to any BBS of your choice, provided that you do not make any
changes to the contents of the archive (ZIP file). The archive and its
individual contents may not be used by any service that charges any money
whatsoever, without the written permission of the author.
REGISTRATION
____________
I am not a subscriber to the "Crippleware" concept, and this program
reflects that philosophy. This is a full-featured program, whose
functionality is not hampered in any way, whether you register it or
not. It is only $15 to register this door. There is a delay that
will be removed upon registration.
THANKS
--------------
Special thanks goes out for my wife who is definitely a
"Computer Widow".
Ted Freeman the author of DOORFRAME, a first class BBS Doors
Development Library.
My BBS users who have had to endure constant badgering to help me
test the programs that I have written.
A *VERY SPECIAL THANKS* to Mustang! Software for developing the
greatest BBS Software on the market, WILDCAT! 3.0.